翻訳と辞書
Words near each other
・ Associated Hebrew Schools of Toronto
・ Associated Humber Lines
・ Associated Independent Colleges
・ Associated Independent Recording
・ Associated Kyoto Program
・ Associated Legendre polynomials
・ Assistive eating devices
・ Assistive listening device
・ Assistive Media
・ Assistive technology
・ Assistive Technology Acts
・ Assistive technology and sports
・ Assistive Technology for Deaf and Hard of Hearing
・ Assistive Technology Industry Association
・ Assistive technology service provider
Assistive Technology Service Provider Interface
・ Assita Toure
・ ASSITEJ
・ Assiti Shards series
・ Assiut Airport
・ Assiut Barrage
・ Assiut University
・ Assize (Scotland)
・ Assize of Arms
・ Assize of Arms of 1181
・ Assize of Arms of 1252
・ Assize of Bread and Ale
・ Assize of Clarendon
・ Assize of darrein presentment
・ Assize of mort d'ancestor


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Assistive Technology Service Provider Interface : ウィキペディア英語版
Assistive Technology Service Provider Interface

Assistive Technology Service Provider Interface (AT-SPI) is, as was the intention from the beginning, a platform-neutral framework for providing bi-directional communication between assistive technologies (AT) and applications.〔(【引用サイトリンク】 ATK/AT-SPI SIG Overview )〕 It is the de facto standard for providing accessibility to free and open desktops, like GNU/Linux or OpenBSD, led by the GNOME Project.
One common nomenclature to explain an accessibility framework is a usual client-server architecture. In that way, Assistive Technologies (ATs) like screen readers, would be the clients of that framework, and computer applications would be the server. In this architecture, client and server need to communicate with each other, usually using the IPC technology of the platform. Ideally the accessibility framework exposes this to the client and server in a transparent way.
Usually the API for both client-side and server-side applications are the same, and the accessibility framework provides a client-side and a server-side implementation of that API. In the case of GNOME, there are two different APIs, one for the client-side (AT-SPI) and a different one for the server-side (Accessibility Toolkit (ATK)) due to historical reasons related to the underlying technologies.
==Implementations==

AT-SPI was originally designed for using CORBA, an object-based IPC/RPC technology, for its transport protocol. The AT-SPI specification itself was tied to CORBA as it was defined in CORBA IDL. AT-SPI used the GNOME project own fast and lightweight CORBA implementation, ORBit, and its own framework for creating CORBA components, Bonobo.〔(【引用サイトリンク】url=http://www.mit.edu/~rjc/orca-docs.html )
The GNOME project decided that the 3.0 release will be free of ORBit and Bonobo meaning a D-Bus AT-SPI solution was required.〔(【引用サイトリンク】url=https://wiki.gnome.org/ThreePointZero/Plan )〕〔(【引用サイトリンク】url=https://wiki.gnome.org/DevGnomeOrg/Gnome3PortingGuide )〕 In an effort to move AT-SPI forward, a D-Bus project was started in November 2006. This took the form of a performance and design review available on the GNOME wiki. Work began on the implementation in May 2007.〔(【引用サイトリンク】url=https://wiki.linuxfoundation.org/en/AT-SPI_on_D-Bus#Background )〕 The D-Bus version of AT-SPI, AT-SPI version 2, was released along with GNOME 3.0 in April 2011.〔(【引用サイトリンク】url=http://www.gnome.org/press/2011/04/gnome-3-0-released-better-for-users-developers-3/ )〕〔(【引用サイトリンク】url=https://git.gnome.org/browse/at-spi2-atk/log/?h=gnome-3-0 )

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Assistive Technology Service Provider Interface」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.